-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Parquet-Exporter helm chart #195
base: main
Are you sure you want to change the base?
Conversation
charts/parquet-exporter/Chart.yaml
Outdated
@@ -0,0 +1,24 @@ | |||
apiVersion: v2 | |||
name: parquet-exporter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could we make this "opencost-parquet-exporter"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That will have a ripple effect in the templates, but I prefer the verbosity/specificity
charts/parquet-exporter/Chart.yaml
Outdated
@@ -0,0 +1,24 @@ | |||
apiVersion: v2 | |||
name: parquet-exporter | |||
description: A Helm chart for Kubernetes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"OpenCost Parquet Exporter"
charts/parquet-exporter/README.md
Outdated
@@ -0,0 +1,38 @@ | |||
# parquet-exporter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we make the title and the path charts/opencost-parquet-exporter
to match the repository?
charts/parquet-exporter/README.md
Outdated
|
||
| Key | Type | Default | Description | | ||
|-----|------|---------|-------------| | ||
| activeDeadlineSeconds | int | `3600` | Keep job runnig (from start time) for [activeDeadlineSeconds] | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"running"
charts/parquet-exporter/values.yaml
Outdated
- name: OPENCOST_PARQUET_S3_REGION | ||
value: YOUR_S3_BUCKET_REGION_NAME_CHANGE_ME | ||
- name: OPENCOST_PARQUET_SVC_HOSTNAME | ||
value: opencost.opencost.svc.cluster.local. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there supposed to be a trailing "."?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. The dot at the end means the dns search-domain will not be appended and this is a fully qualified hostname.
charts/parquet-exporter/Chart.yaml
Outdated
@@ -0,0 +1,24 @@ | |||
apiVersion: v2 | |||
name: parquet-exporter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That will have a ripple effect in the templates, but I prefer the verbosity/specificity
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add new line at the end
charts/parquet-exporter/values.yaml
Outdated
ttlSecondsAfterFinished: 14400 | ||
# -- ServiceAccount use to run this pod | ||
serviceAccount: | ||
name: opencost |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the exporter depend on the opencost service account? I couldn't find something related to this in the exporters repo README.md.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I took that over from @lmello 's code. I have not looked into the actual requirements for the AWS S3 integration but I have to assume that its there for this purpose. Also it is not required to interact with the opencost application.
The service account key/value pair is optional however. Would you rather have me remove it from the values yaml or adjust the description to state that its an optional parameter`
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the service account is not required, I would leave it empty. Maybe also change the key to existingServiceAccount? Otherwise I would assume that it creates the service account by itself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you. Ill change accordingly!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add new line at the end
charts/parquet-exporter/values.yaml
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add new line at the end
… tag to :main, implement review comments
…sed when not empty
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did not test it on my cluster, but the code LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the values need to move to opencost-parquet-exporter
, but I didn't test.
{{/* | ||
Common labels | ||
*/}} | ||
{{- define "parquet-exporter.annotations" -}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do the "parquet-exporter" references need to be changed to "opencost-parquest-exporter" across the board?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be consistent with actual chart name. I'll update accordingly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
This pull request has been marked as stale because it has been open for 60 days with no activity. Please remove the stale label or comment or this pull request will be closed in 5 days. |
This pull request has been marked as stale because it has been open for 60 days with no activity. Please remove the stale label or comment or this pull request will be closed in 5 days. |
I will review this PR after the change to the parquet export repo is merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fix the trailling whitespaces:
Error: 1:56 [trailing-spaces] trailing spaces
Error: 8:22 [trailing-spaces] trailing spaces
Error: 12:68 [trailing-spaces] trailing spaces
Error: 27:12 [trailing-spaces] trailing spaces
Error: 59:209 [trailing-spaces] trailing spaces
Error: 62:117 [trailing-spaces] trailing spaces
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This pull request has been marked as stale because it has been open for 60 days with no activity. Please remove the stale label or comment or this pull request will be closed in 5 days. |
Moved from opencost/opencost-parquet-exporter#10
Hey everyone,
I've created a first draft of a helm chart for the parquet-exporter. I do not have a setup where I can use AWS as of now, therefore the actual push to a S3 bucket is not yet tested. However, I was able to install the chart and run the cronjob in my minikube.
Used helm-docs to create a rough documentation around the chart
The chart itself is relatively straight forward I think
Let me know what you think!